<html>
<head><meta charset="utf-8"><title>stabilization to wrong version · t-release · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/index.html">t-release</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html">stabilization to wrong version</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="220958472"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220958472" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220958472">(Dec 26 2020 at 10:15)</a>:</h4>
<p>Hey hey,</p>
<p><a href="https://github.com/rust-lang/rust/issues/79022">#79022</a> stabilized some library feature in 1.50, but was merged right after <a href="https://github.com/rust-lang/rust/issues/80366">#80366</a> which bumped the version to 1.51 (which got priority due to rollup=never). This was noticed by accident, but could've easily been missed. Is there anything we can do to avoid this in the future?</p>



<a name="220961391"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220961391" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220961391">(Dec 26 2020 at 12:00)</a>:</h4>
<p>I think we need support in bors for pre-merge scripts, which could be used for e.g. running rustfmt, sed replacing $VERS with the merged version... maybe some other things.</p>



<a name="220961392"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220961392" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220961392">(Dec 26 2020 at 12:01)</a>:</h4>
<p>But nothing right now</p>



<a name="220973242"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220973242" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Noah Lev <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220973242">(Dec 26 2020 at 18:02)</a>:</h4>
<p>Ideally this would be handled automatically somehow, but a manual thing that might help is, before <code>r+</code>ing the version bump: close the tree, manually make sure none of the PRs stabilize something in the previous version, if they do then give them higher priority than the treeclose, then wait for all of them to be merged, <code>r+</code> the version bump with high priority (e.g. <code>p=10000</code>), and then open the tree.</p>



<a name="220973261"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220973261" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Noah Lev <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220973261">(Dec 26 2020 at 18:03)</a>:</h4>
<p>Not sure if that's too much effort or too involved to be worth it, but it's an idea.</p>



<a name="220973314"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220973314" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220973314">(Dec 26 2020 at 18:04)</a>:</h4>
<p>closing the tree for every stabilization seems like a waste though</p>



<a name="220973315"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220973315" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220973315">(Dec 26 2020 at 18:04)</a>:</h4>
<p>I would rather just wait the week for the beta bump</p>



<a name="220975070"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220975070" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Noah Lev <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220975070">(Dec 26 2020 at 19:00)</a>:</h4>
<p>What do you mean?</p>



<a name="220976241"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220976241" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220976241">(Dec 26 2020 at 19:36)</a>:</h4>
<p>I honestly don't care enough about versions being right to add such a manual step; my goal is to entirely automate releases at some point and this would work against that. I don't think any manual solution is worth the investment of time/energy from our limited set of releasers.</p>



<a name="220988565"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220988565" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Noah Lev <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220988565">(Dec 27 2020 at 02:03)</a>:</h4>
<blockquote>
<p>my goal is to entirely automate releases at some point and this would work against that</p>
</blockquote>
<p>This would be a temporary solution, so I'm not sure how it works against that.</p>
<blockquote>
<p>I don't think any manual solution is worth the investment of time/energy from our limited set of releasers.</p>
</blockquote>
<p><span aria-label="+1" class="emoji emoji-1f44d" role="img" title="+1">:+1:</span> I was just making a suggestion in case it was worth it :)</p>
<p>Perhaps I thought that the versions being mismatched was more of an issue than it actually is.</p>



<a name="220990259"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220990259" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220990259">(Dec 27 2020 at 03:00)</a>:</h4>
<p>It works against it by providing something that's not possible to automate which makes automation a regression and as such less palatable.</p>



<a name="220990274"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220990274" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220990274">(Dec 27 2020 at 03:01)</a>:</h4>
<p>Generally anything that touches release work needs to strive to need as little human input that's not checklist as possible, because even if it's a human doing it release work is very critical and we must not get it wrong. Keeping it simple is the way to do that.</p>



<a name="220990336"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220990336" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220990336">(Dec 27 2020 at 03:03)</a>:</h4>
<p>I've not personally ever seen significant value to version numbers in documentation, but I use nightly exclusively pretty much or latest stable. IMO, if you care about version compatibility you must test against that version and stabilization/missing API errors are usually really obvious. I would rather stop listing version numbers than put contributor time into them personally.</p>



<a name="220990384"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220990384" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220990384">(Dec 27 2020 at 03:04)</a>:</h4>
<p>version numbers are useful for <em>finding</em> what your MSRV is without having to test each release one at a time</p>



<a name="220990390"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220990390" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220990390">(Dec 27 2020 at 03:05)</a>:</h4>
<p>agreed you should test it in the end, but testing 50 releases one at a time is painful</p>



<a name="220992353"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/241545-t-release/topic/stabilization%20to%20wrong%20version/near/220992353" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/241545-t-release/topic/stabilization.20to.20wrong.20version.html#220992353">(Dec 27 2020 at 04:14)</a>:</h4>
<p>I am confused - for almost all things, you can bisect, and then 50 is <em>at most</em> 6 points (and 2018 edition use cuts that to 4ish).</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>